From: Florian Müllner <fmuellner@gnome.org>
Date: Wed, 3 Jun 2015 10:30:12 +0000 (+0200)
Subject: network: Initialize primary and VPN connections on startup
X-Git-Tag: archive/raspbian/50.5-1+rpi1~1^2~1013^2^2~700
X-Git-Url: https://dgit.raspbian.org/%22http://www.example.com/cgi/%22/%22http:/www.example.com/cgi/%22?a=commitdiff_plain;h=d0bab1f7acfd76b5634013c0f16c19570ac2932e;p=gnome-shell.git

network: Initialize primary and VPN connections on startup

We only connect to the corresponding property notifications after both
Client and RemoteSettings are ready, so we may miss the initial signal
emission. Make sure to pick up the connections in this case to fix the
network indicator not showing up.

https://bugzilla.gnome.org/show_bug.cgi?id=772249
---

diff --git a/js/ui/status/network.js b/js/ui/status/network.js
index 6f42aea06..fee703bed 100644
--- a/js/ui/status/network.js
+++ b/js/ui/status/network.js
@@ -1632,6 +1632,8 @@ const NMApplet = new Lang.Class({
         this._readConnections();
         this._readDevices();
         this._syncNMState();
+        this._syncMainConnection();
+        this._syncVPNConnections();
 
         this._client.connect('notify::manager-running', Lang.bind(this, this._syncNMState));
         this._client.connect('notify::networking-enabled', Lang.bind(this, this._syncNMState));